I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?

Applications are becoming more and more sophisticated as languages such as Python open the doors to the world of programming for people who have the creative vision but always felt actually writing code was beyond their grasp.

A large part of any programs success is based on how well it can react to the events which it has been programmed to understand and listen for.

A good example of an event would be when the user clicks a button on the applications window. What happens when that button is clicked?

Well, the first thing that happens is the operating system sends out a message to let any listening software know that the button was clicked. Next, your application needs to do something in response to that event.

As developers we are overwhelmed with the number of language choices made available to us. It wasn't so long ago that C and it's object oriented sibling C++ where the mainstay of any programmer. Now though we have languages which make certain tasks so easy and simple that we simply cannot afford to ignore them.

In this article we are going to look at the overall differences between Python, Perl and TCL. All formidable and worthy in their own right, but each one has been designed to suit a specific programming need.

1)– Perl is the most mature out of the three languages we are looking at in this article. It was originally designed for processing textual data, and it does so extremely well. Of course Perl has grown over time and can be used for a multitude of different programming scenarios.

Passbook is one of the newest features of the iPhone. What many people were offput by standards today is that we rely too much on disposable tickets, and the like, such as when you go to the airport for a boarding pass, or a movie ticket. Apple strove to solve that with a new application that is bundled with the newest update: Passbook.

Passbook offers everything you need, especially when a ticket, coupon, or gift card is needed. When you first open the application you are greeted by a sampling of applications that support Passbook, and its features. To begin, install the particular application you want to use. For example, we will be going with the Starbucks application to satiate our coffee needs every morning, as we have a gift card to spend.

Open up the freshly downloaded application, and get ready to be blown away. Like most applications, especially when it has to do with airlines, or coffee, you are almost always required to sign up for a respective account. Don’t worry, it is easy. All you will be asked is to fill out your email, a password, and other miscellaneous information to identify you when you lose your password or others.

Once you have finished signing up, you’re ready to roll. It will prompt you to enter a gift card that you already own, or begin a digital gift card. If you don’t have a gift card, you can start a digital gift card (or, as many may call it: a prepaid card), and pay for your coffee in a fast, and efficient way. Just tap on “Tap to Pay” when you are ready to pay, and tap again after you have paid. It’s really that easy.